Repository navigation
ci: 🔒 stage releases on npm through Trusted Publishing - #65
Merged
Merged
Conversation
The release workflow published with an NPM_TOKEN (npm stops 2FA-bypass tokens from publishing in January 2027), on Node 20 and pnpm 9, with an unfrozen install, no tests, and under `latest`: a 2.0.0 beta would have replaced 1.0.0 for a plain install. A `v*` tag now runs the whole CI first. Then the workflow checks that the tag is the version in package.json and that the package has every file package.json points to, and stages the version on npm through Trusted Publishing (OIDC, no stored token), a prerelease under its identifier (`beta`) and a plain version under `latest`. Nothing is public until a maintainer approves it with 2FA (`npm stage approve`, as npm recommends: the trusted publisher only allows staging), so the GitHub release with the changelog is a draft to publish then. prepublishOnly ran `qwik build`, which also ran `lint`, the one that writes the fixes: it now only builds the types and the library. The release commit follows the history (`chore(release): 🔖 v…`), and `np`, unused, is gone. CONTRIBUTING has the release steps.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The release workflow published with an NPM_TOKEN (npm stops 2FA-bypass
tokens from publishing in January 2027), on Node 20 and pnpm 9, with an
unfrozen install, no tests, and under
latest: a 2.0.0 beta would havereplaced 1.0.0 for a plain install.
A
v*tag now runs the whole CI first. Then the workflow checks that thetag is the version in package.json and that the package has every file
package.json points to, and stages the version on npm through Trusted
Publishing (OIDC, no stored token), a prerelease under its identifier
(
beta) and a plain version underlatest. Nothing is public until amaintainer approves it with 2FA (
npm stage approve, as npm recommends:the trusted publisher only allows staging), so the GitHub release with
the changelog is a draft to publish then.
prepublishOnly ran
qwik build, which also ranlint, the one thatwrites the fixes: it now only builds the types and the library. The
release commit follows the history (
chore(release): 🔖 v…), andnp,unused, is gone. CONTRIBUTING has the release steps.
Stack created with GitHub Stacks CLI • Give Feedback 💬